207 This is the next statement that will be executed.
208 This code has called into another function. When that function is finished, this is the next statement that will be executed.
209 This is the next statement that will be executed. To change which statement is executed next, drag the arrow. This may have unintended consequences.
210 Disable All Breakpoints
211 (no condition)
212 The following breakpoint may cause the program to run very slowly while being debugged:\n\n%1\n\nIs this OK?
213 There is no source code or disassembly available for the current location.
214 There is no source code available for the current location. To automatically display disassembly, go to the Debugging page in Tools->Options.
215 There is no source code available for the current location.
216 Unable to go to the breakpoint. %1
217 There is no source code available for the current location.
222 Unable to set the current program.
224 Unable to set the current thread.
226 Unable to set the current stack frame.
232 This thread has called into a function that cannot be displayed.
233 Unmanaged debugging is not available.
236 Module
238 Address
240 Function
252 Index
254 Function
256 Language
257 < More... (The first %1 of %2 items were displayed.) >
300 Debugging isn't possible due to an incompatability within the CLR implementation.
301 Debugging isn't possible because a kernel debugger is enabled on the system. Click Help for more information.
302 Debugging isn't possible because a kernel debugger is present on the system.
303 The maximum number of processes is already being debugged.
304 Interop debugging is not supported on this platform.
305 Script debugging is disabled for the application you are debugging. Please uncheck the 'Disable script debugging' option on the Internet Options dialog box (Advanced page) for Internet Explorer and restart the process.
306 There are no script programs running in the application you are debugging. Restart the application if you have unchecked the 'Disable script debugging' option on the Internet Options dialog box (Advanced page) for Internet Explorer.
307 The .NET debugger has not been installed properly. The most probable cause is that mscordbi.dll is not properly registered. Click Help for more information on how to repair the .NET debugger.
308 There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching.
309 There is no debuggable script code running in the application you are debugging. This is most likely because of your default DCOM access permissions. See help for more information.
310 There is no debuggable script code running in the application you are debugging. This is most likely because the debugger is not able to contact the 'Machine Debug Manager' service. See help for more information.
311 The debugger cannot access the script application that you are debugging. See help for more information.
312 The web server has been locked down and is blocking the DEBUG verb, which is required to enable debugging. Click Help for more information.
313 Debugging failed because integrated Windows authentication is not enabled. Click Help for more information.
314 ASP debugging is disabled because the ASP process is running as a user that does not have debug permissions. Click Help for more information.
315 The remote computer does not have a CLR version which is compatible with the remote debugging components. To install a compatible CLR version, see the instructions in the 'Remote Components Setup' page on the Visual Studio CD.
500
501 Unable to update the breakpoint.
502 Execution has stopped at the beginning of the program because one or more breakpoints could not be set.
503 An exception containing the specified string was not found.
504 There are no more exceptions containing the specified string.
505 Unable to connect to the machine '%1'. %2
506 Unable to disable all the breakpoints. %1
507 Unable to attach to the process. %1
508 The debugger cannot display source code or disassembly for the current location.
509 Error
510 Enter a function name.
511 The machine cannot be found on the network.
512 Access is denied. Verify that you are an administrator or a member of the 'Debugger Users' group on the machine you are trying to debug. After being added to the 'Debugger Users' group, you must log off and log back on for the setting to apply.
513 A previous expression evaluation is still in progress.
514 Machine Debug Manager (mdm.exe) is not installed or failed to start properly. Click Help for more information.
515 The machine is not currently available on the network.
516 A debugger is already attached.
517 The process does not have sufficient privileges to be debugged.
518 The desktop cannot be debugged.
519 The debugger is not properly installed. Run setup to install or repair the debugger.
520 Unable to break into the process '%1'. %2
521 Unable to break into the process. %1
522 Unable to detach from the process '%1'. %2
523 Unable to detach from the process. %2
524 Cannot run to the specified location.
525 Unable to evaluate the expression. %1
526 Unable to start program '%1'.\n\n%2
527 Unable to set the next statement to this location. %1
528 Unable to open input file '%1'.
529 Unable to open output file '%1'.
530 The exception name is not valid.
531 Unable to attach to application '%1' (PID: %3) on machine '%2'.\n\nDo you want to continue anyway?
532 Unable to attach to machine '%1'.\n\nDo you want to continue anyway?
533 Unable to debug the process at this time.
534 Unable to execute the statement because the current thread is not executing code.
535 Invalid expression.
536 Unable to restart debugging. %1
537 The specified hit count target is not valid.
538 Unable to set exceptions.
539 Unable to start debugging. A program to debug has not been specified.
540 Enter a valid file name.
541 Enter a breakpoint location.
542 Memory could not be displayed for the expression.\n%1
543 The file name must be an absolute path, such as 'c:\dir\file.ext' or '\\server\share\dir\file.ext'
544 Disassembly cannot be displayed for the source location. %1
545 MSVCMON is either not running on the remote machine or is running in pipe mode.
546 The process has been terminated.
547 The IP address for the remote machine is not valid.
548 The remote machine is not responding.
549 The remote machine name is not specified.
550 Other programs cannot be debugged while post-mortem debugging.
551 All of the threads are frozen. Use the Threads window to unfreeze at least one thread before attempting to step or continue the program.
552 The debugger transport DLL cannot be loaded.
553 MSPDB71.dll cannot be loaded.
554 MSDIS140.dll cannot be loaded.
555 NatDbgEE.dll cannot be loaded.
556 NatDbgDM.dll cannot be loaded.
557 Output cannot be redirected because the specified file is invalid.
558 Output cannot be redirected because the syntax is incorrect.
559 The remote debugger is not an acceptable version.
560 A breakpoint could not be inserted at this location.
561 Some breakpoints could not be deleted and have been disabled instead.
562 No source file
563 Unavailable when debuggee is running.
564 Unavailable when not debugging.
565 Please enter an expression.
566 The specified address cannot be displayed. %1
567 One or more breakpoints could not be deleted.
568 The call stack is not available at this time.
569 The call stack cannot be displayed. %1
570 The call stack is empty.
571 Unable to list programs. %1
572 Unable to list threads. %1
573 Unable to list memory. %1
574 Unable to list registers. %1
575 Unable to set radix.
576 Unable to list disassembly. %1
577 This operation is not supported during postmortem debugging.
578 The source code cannot be displayed. %1
579 The specified radix is not recognized.
580 Specify an address.
581 The debugger cannot continue running the program. %1
582 The end address '%1' cannot be evaluated. %2
583 Could not write value to memory
584 The Visual Studio debugger proxy service was not running when debugging was started.
585 The expression evaluation took too long.
586 There is no executable code at this location in the source code.
587 The expression cannot be evaluated while in run mode. %1
588 The debugger cannot step program execution. %1
589 Unable to detach from one or more programs. %1
590 Unable to stop debugging. %1
591 The breakpoint could not be set. %1
592 %1 does not support breakpoint conditions.
593 %1 does not support breakpoint hit counts.
594 %1 does not support address breakpoints.
595 Unable to go to the source code of the breakpoint.
596 The expression cannot be evaluated while in design mode.
597 %1 does not support call stack breakpoints.
598 %1 does not support function breakpoints.
599 %1 does not support data breakpoints.
600 Unable to go to the disassembly of this breakpoint.
601 The specified file is an unrecognized or unsupported binary format.
602 %1 does not support disassembly.
603 Disassembly cannot be displayed. %1
604 This is not a valid location for a breakpoint.
605 The current program type does not support disassembly.
606 The specified count is too large. The maximum count is %1.
607 Cannot detach from one or more programs. Terminate them instead?
608 (Disassembly cannot be displayed in run mode.)
609 Unable to connect to '%1'. %2
610 The specified address does not exist in disassembly.
611 Cannot detach from one or more programs: %1\n\nTerminate them instead?
612 Remote Procedure Call Step
613 Cannot run to the specified location.
614 Unable to start debugging.
615 The program has not yet finished initializing. Try again later.
616 The Machine Debug Manager service is disabled.
617 The debugger is not properly installed. Run setup to install or repair the debugger.
618 Cannot step to the specific location. %1
619 Access is denied. This seems to be because the 'Network access: Sharing and security model for local accounts' security policy does not allow users to authenticate as themselves. This can be configured with the 'Local Security Settings' administration tool.
620 A security check failed because the IIS Admin Service did not respond. To fix this, repair or remove IIS, and restart your computer. See Help for more details on how to do this.
4958 No data available
4959 Debugger Data Changed
4960 Registers
4961 Modules
4963 Name
4964 Address
4965 Path
4966 Order
4967 Version
4968 Information
4969 Program
4970 Executables (*.exe)|*.exe|
4971 Find Program to Debug
4972 Browse for Working Directory
4973 The program specified does not exist or is only a directory. Make sure to include the full path?
4974 The debug session could not be created. %1
4975 The working directory specified does not exist or is not a directory.
4976 Save Dump As
4977 This
4978 Memory Edit
4979 The thread %1 has exited with code %2.
4980 The program '%1' has exited with code %2.\n
4981 Edit and Continue will not be supported while debugging. %1
4982 Memory Unreadable
4983 Unable to break execution. %1
4984 There is not a loaded project that can be launched.
4985 An initial stopping location was not found in the program. To stop during program execution, first set a breakpoint and then start running the program.
4986 Register Data
4987 No memory.
4988 Detach from this process
4989 Terminate this process
4990 Unable to terminate process '%1'. %2
4991 Unable to terminate process. %1
4992 Unable to start Just-In-Time debugging. %1
4993 Unknown Exception Type
4994 Edit and Continue was unable to apply your code changes. See the output window or task list for details. \n\nClick Build to stop debugging and rebuild your code. \nClick OK to return to break mode.
4995 No expression.
4996 Edit and Continue was unable to apply your code changes. See the output window or task list for details. \n\nClick Build to stop debugging and rebuild your code. \nClick Ignore to continue executing the original code. \nClick OK to return to break mode.
4997 Applying Code Changes...
4998 Apply code changes succeeded
4999 Unable to start debugging on the web server. %1
5000 Debugging
5001 General
5002 Find Source
5003 Edit and Continue
5004 Native
5005 Edit and Continue
5006 Stale Code
5007 Find Symbol
5008 The option to only stop execution of the current program has been specified. Therefore, the current program cannot be changed.
5009 <Unknown Transport>
5010 Na&me:
5011 Na&me:
5012 This program type is required to handle the exception you are debugging and cannot be unselected.
5013 The name of the file entered must match that of the original source file.
5014 '%1' is not a valid working directory.
5015 Cannot find port. Check the remote machine name.
5016 The process has been soft broken.
5017 CPU\nEffective Address
5018 Minidump (*.dmp)|*.dmp|Minidump with Heap (*.dmp)|*.dmp|
5019 Old version of DBGHELP.DLL found, does not support minidumps.
5020 The Visual Studio debugger proxy service cannot be used in a Terminal Server session.
5021 The Visual Studio debugger proxy service failed to impersonate the current user.
5022 Unable to automatically attach to %1. \n%2
5023 Server side-error occurred on sending debug HTTP request.
5024 You do not have permissions to debug the server.
5025 Could not start ASP.NET or ATL Server debugging.
5026 The project is not configured to be debugged.
5027 <Unknown Module>
5028 Process '%1' is not running on %2.
5029 The expression has not yet been translated to native machine code.
5030 Register NAT
5031 The next statement cannot be changed when stopped at an exception.
5032 There is no MSVCMON on the remote machine running under the current user context.
5033 The switch value '%1' should either be 'Yes' or 'No'.
5034 The switch value '%1' should be a number.
5035 Unable to run to the specified address. %1
5036 Just-In-Time
5037 Processes cannot be displayed. %1
5038 There is no code at the supplied location.
5039 Unable to stop debugging %1. \n%2
5040 The server does not support debugging of ASP.NET or ATL Server applications. Click Help for more information on how to enable debugging.
5041 Could not start ASP.NET or ATL Server debugging.
5042 The next statement cannot be set to another function.
5043 Unable to start debugging.\n\n%1
5044 Session
5045 The file cannot be opened.
5046 This operation will first switch to the top frame of the call stack and then set the next statement to a different function. Are you sure?
5047 The debugger is not properly installed on machine '%1'.
5048 <Unknown Error>
5049 Timestamp
5050 RPC Debugging failed to initialize. You must be in Design mode to enable RPC Debugging.
5052 Stepping to or from system code on a machine running Windows 95/Windows 98/Windows ME is not allowed.
5053 Debug Source Files
5054 Search these paths for source files:
5055 Debug Symbol Files
5056 Search these paths for symbol files:
5057 Process: %1\n%2\n\nProgram types successfully attached are:\n%3\nProgram types that failed to attach are:\n%4
5058 The requested attach was not completely successful.
5059 Automatically attaching to support this behavior was not completely successful.
5060 Transport
5061 Machine/Port
5062 Click Help for more information.
5064 Debugger component on server could not find this machine. Please verify that DCOM is enabled.
5065 Debugger component on server could not find this machine.
5066 The debugger component on the server failed to connect to the local machine. Please verify that you are logged onto the server through Terminal Services or that you are logged on to the server at console. Click help for more information.
5067 The debugger component on the server failed to connect to the local machine. Click help for more information.
5068 Debugger component on server could not connect to this machine because there was no available authentication service. Please verify that you have set access control to User-Level Access Control in your computer's network settings.
5069 Debugger component on server could not connect to this machine because there was no available authentication service.
5070 There appears to be no suitable logon session on the server. Please verify that you are logged on to the server through Terminal Services or that someone is logged into the server locally.
5071 Mini-Dumps cannot be read on this system. Please use a Windows NT based system
5072 There appears to be no suitable logon session on the server. Please verify that you are logged on to the server through Terminal Services or that you are logged onto the server locally.
5073 Attaching to processes in other users sessions is not allowed. Administrators can enable this feature. Consult the help for more information.
5074 The debugger cannot connect to remote machines using the default transport without user-level access control. For native debugging, you can use TCP/IP transport.
5075 Attaching to a process in a different terminal server session is not supported on this system. Try remote debugging to the machine using pipe or tcp/ip transport and running msvcmon in that session.
5076 Save Dump on Remote Machine As
5077 Please wait until Edit and Continue is complete before exiting, or select Stop Applying Code Changes from the Debug menu.
5078 \nTo attach the debugger from the command line, use:\n vs7jit.exe -p <pid>\n
5079 User Profile
5084 You do not have privileges to debug the web server process.
5085 Unable to map the debug start page URL to a machine name.
5086 You do not have permission to debug the application. The URL for this project is in the Internet zone. Click Help for more information.
12000 The dbgproxy service can be started from a command prompt by entering 'net start dbgproxy'.
12001 Refresh the process list before attempting another attach.
12002 You may also want to refer to the ASP.NET and ATL Server debugging topic in the online documentation.
12003 Verify that you are a member of the 'Debugger Users' group on the server.
12004 Make sure the server is operating correctly. Verify there are no syntax errors in web.config by doing a Debug.Start Without Debugging. You may also want to refer to the ASP.NET and ATL Server debugging topic in the online documentation.\n
12005 Verify that ASP.NET or ATL Server is correctly installed on the server.
12006 For ASP.NET projects:\n1. Verify that you have a valid project file called 'Web.config' for the URL specified.\n2. Verify that 'debug' is set to 'true' in the 'Web.config' file.\n3. Verify that the 'DEBUG' verb is associated with the '.aspx' extension.\n\nFor ATL Server projects, verify that the 'DEBUG' verb is associated with your ISAPI extension.\n
12007 Verify that Visual Studio .NET remote debugger components have been installed on the server. To work around this issue, start without debugging and then attach to the process.
12008 Verify your JIT settings. These settings can be found in the JIT Debugging Settings dialog box. On the Tools menu, click Options and click the Debugging folder. Click the General page, and click the JIT Settings button.
12009 Contact an Administrator to get the debug privileges on the server. You may also want to refer to the ASP.NET and ATL Server debugging topic in the online documentation.
13000 Could not initialize debugger automation.
13001 Could not create object.
13002 No location specified for new breakpoint. Supply a function name, file location, data expression, or address.
13003 Multiple locations specified for new breakpoint.
13004 Object no longer valid.
13005 Expression was valid but could not be evaluated.
13006 No valid context in which to evaluate the expression.
13007 Unable to execute method at this time.
13008 Not allowed while inside debugger event handler.
13009 No solution opened.
13010 Invalid expression.
13011 Invalid statement.
13012 Function name not valid for new breakpoint.
13013 File position not valid for new breakpoint.
13014 Address not valid for new breakpoint.
13015 Hit count values not valid for new breakpoint.
13016 Data expression not valid for new breakpoint.
13017 Language not valid for new breakpoint.
13018 Count must be supplied when specifying a data expression.
13019 Line and column information must be supplied when specifying a filename.
13020 Condition type must be supplied when specifying a condition.
13021 Hit count type must be supplied when specifying a hit count.
13022 Please wait until the debuggee has finished loading, and try again.
13023 The process does not contain any programs.
13024 Can not evaluate script expressions while thread is stopped in the CLR.
13025 A stepping breakpoint could not be set
13026 NatDbgDM.dll being loaded has an incorrect version.
13027 The debugger transport dll being loaded has an incorrect version.
13028 MSVCMON is either not running on the remote machine or is running in tcp/ip mode.
